Compare Page

Referential integrity

Characteristic Name: Referential integrity
Dimension: Consistency
Description: Data relationships are represented through referential integrity rules
Granularity: Record
Implementation Type: Rule-based approach
Characteristic Type: Declarative

Verification Metric:

The number of referential integrity violations per thousand records

GuidelinesExamplesDefinitons

The implementation guidelines are guidelines to follow in regard to the characteristic. The scenarios are examples of the implementation

Guidelines: Scenario:
Implement and maintain foreign keys across tables (Data sets) (1) Implementation of foreign keys
Implement proper validation rules/Automated suggestions of values based on popular value combinations, to prevent incorrect references of foreign keys (1) The attribute Customer_Zip_Code of the Customer relation contains the value 4415, instead of 4445; both zip codes exist in the Zip_Code relation
Implement validation rules for foreign keys of relevant tables in case of data migrations (1) Error logs are generated for foreign key violations.
Implement proper synchronising mechanisms to handle data updates when there are concurrent operations or distributed databases. (1) Locking mechanisms to data objects while being updated
Ensure the consistency of the data model when changes are done to process model (software) (1) Data dictionary provides the FDs and CFDs

Validation Metric:

How mature is the creation and implementation of the DQ rules to maintain referential integrity

These are examples of how the characteristic might occur in a database.

Example: Source:
the name of the city and the postal code should be consistent. This can be enabled by entering just the postal code and filling in the name of the city systematically through the use of referential integrity with a postal code table Y. Lee, et al., “Journey to Data Quality”, Massachusetts Institute of Technology, 2006.
A company has a color field that only records red, blue, and yellow. A new requirement makes them decide to break each of these colors down to multiple shadings and thus institute a scheme of recording up to 30 different colors, all of which are variations of red, blue, and yellow. None of the old records are updated to the new scheme, as only new records use it. This data- base will have inconsistency of representation of color that crosses a point in time. J. E. Olson, “Data Quality: The Accuracy Dimension”, Morgan Kaufmann Publishers, 9 January 2003.

The Definitions are examples of the characteristic that appear in the sources provided.

Definition: Source:
The Information Float or Lag Time is acceptable between (a) when data is knowable (create or changed) in one data store to (b) when it is also knowable in a redundant or distributed data store, and concurrent queries to each data store produce the same result. ENGLISH, L. P. 2009. Information quality applied: Best practices for improving business information, processes and systems, Wiley Publishing.
Assigning unique identifiers to objects (customers, products, etc.) within your environment simplifies the management of your data, but introduces new expectations that any time an object identifier is used as foreign keys within a data set to refer to the core representation, that core representation actually exists. LOSHIN, D. 2006. Monitoring Data quality Performance using Data Quality Metrics. Informatica Corporation.
i.e. integrity rules. Data follows specified database integrity rules. PRICE, R. J. & SHANKS, G. Empirical refinement of a semiotic information quality framework. System Sciences, 2005. HICSS'05. Proceedings of the 38th Annual Hawaii International Conference on, 2005. IEEE, 216a-216a.

 

Ease of data access

Characteristic Name: Ease of data access
Dimension: Availability and Accessability
Description: Data should be easily accessible in a form that is suitable for its intended use.
Granularity: Information object
Implementation Type: Process-based approach
Characteristic Type: Usage

Verification Metric:

The number of tasks failed or under performed due to lack of ease in data access
The number of complaints received due to lack of ease in data access

GuidelinesExamplesDefinitons

The implementation guidelines are guidelines to follow in regard to the characteristic. The scenarios are examples of the implementation

Guidelines: Scenario:
Routinely accessed information to continue operations, should be automatically delivered to stakeholders online without wasting their time to search for it. (1) Daily exchange rates are linked into the accounting application or maintained in a dash board on the accountants desktop.

(2) Production efficiency is made available on a display board in the production floor.

Information needed for management reporting purposes should be identified and catered through built in reports where the users do not have to create the reports themselves. (1) Order status is frequently searched information by different stake holder groups and hence a report is made available with multiple searching criteria.
Facilitate users by providing tools to query the database without using any specific technical knowledge and perform business analytics to bring innovation (1) Technical infrastructure supports the users to develop their own reports based on dynamic information needs without consulting technical staff.
Facilitate the user to filter the relevant information depending on the need. (1) Sales report with filtering criteria for customer and date range.
The interfaces and reports should be created conveniently the users do not have to write complex queries or further process information before usage. (1) Product prices are ordered as per "Relevance" or "Price" to enable an e-commerce customer on a purchase decision

Validation Metric:

How mature is the process of maintaining ease in data access

These are examples of how the characteristic might occur in a database.

Example: Source:
Consider a database containing orders from customers. A practice for handling complaints and returns is to create an “adjustment” order for backing out the original order and then writing a new order for the corrected information if applicable. This procedure assigns new order numbers to the adjustment and replacement orders. For the accounting department, this is a high-quality database. All of the numbers come out in the wash. For a business analyst trying to determine trends in growth of orders by region, this is a poor-quality database. If the business analyst assumes that each order number represents a distinct order, his analysis will be all wrong. Someone needs to explain the practice and the methods necessary to unravel the data to get to the real numbers (if that is even possible after the fact). J. E. Olson, “Data Quality: The Accuracy Dimension”, Morgan Kaufmann Publishers, 9 January 2003.

The Definitions are examples of the characteristic that appear in the sources provided.

Definition: Source:
Accessibility refers to the physical conditions in which users can obtain data Clarity refers to the data’s information environment including appropriate metadata. LYON, M. 2008. Assessing Data Quality ,
Monetary and Financial Statistics.
Bank of England. http://www.bankofengland.co.uk/
statistics/Documents/ms/articles/art1mar08.pdf.
Speed and ease of locating and obtaining an information object relative to a particular activity STVILIA, B., GASSER, L., TWIDALE, M. B. & SMITH, L. C. 2007. A framework for information quality assessment. Journal of the American Society for Information Science and Technology, 58, 1720-1733.
Data are available or easily or quickly retrieved. WANG, R. Y. & STRONG, D. M. 1996. Beyond accuracy: What data quality means to data consumers. Journal of management information systems, 5-33.